Conflict resolution for device-driven management

ABSTRACT

Disclosed are various embodiments for resolving conflicts between workflows in a workflow processing system. A plurality of workflows stored in a workflow queue are evaluated to identify a common dependency of the plurality of workflows. Then, a version hierarchy is created for the common dependency of the plurality of workflows, the version hierarchy identifying multiple versions of the common dependency. In response to execution of a first one of the plurality of workflows stored in the workflow queue, the version hierarchy can be evaluated to identify the most recent version of the common dependency. Then, installation of the most recent version of the common dependency can be initiated.

RELATED APPLICATIONS

Benefit is claimed under 35 U.S.C. 119(a)-(d) to Foreign ApplicationSerial No. 202141003449 filed in India entitled “CONFLICT RESOLUTION FORDEVICE-DRIVEN MANAGEMENT”, on Jan. 25, 2021, by VMware, Inc., which isherein incorporated in its entirety by reference for all purposes.

BACKGROUND

Various challenges can arise in the management of enterprise resourcesusing a management service. Access to the capabilities of a device canbe managed through the administration of compliance rules defined andenforced by the management service. The proliferation of personal tabletand smartphone devices, for example, has resulted in several companiesand organizations allowing employees to use their own devices forenterprise purposes. The use of these personal devices can be associatedwith productivity gains and cost savings. The concept “bring your owndevice” (BYOD) for access to enterprise computing systems may have metinitial resistance due to security concerns, but more and more companiesare now looking to incorporate BYOD policies. This causes enterprises tomanage a growing number of different desktop, tablet, and mobiledevices, along with various platforms and operating systems availablefor adoption by users. Many enterprises include employees that work invarious locations including a traditional workplace, temporary fieldworkplaces, as well as from home. At the same time, complexity ofprocesses utilized for protecting enterprise resources has increased,requiring higher bandwidth for the constant communication of manageddevices with the management service. Personal devices can frequentlylose network connectivity, causing security issues, management failures,and delays. There is a need for a more efficient and effective devicemanagement paradigm.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily drawn to scale, with emphasis instead being placed uponclearly illustrating the principles of the disclosure. In the drawings,like reference numerals designate corresponding parts throughout theseveral views.

FIG. 1 illustrates an example networked environment that provides toolsfor device-driven management, according to various examples describedherein.

FIG. 2 illustrates a flowchart performed by components of the networkedenvironment for device-driven management, according to various examplesdescribed herein.

FIG. 3 illustrates another flowchart performed by components of thenetworked environment for device-driven management, according to variousexamples described herein.

FIG. 4 illustrates an example user interface that provides tools fordevice-driven management using components of the networked environment,according to various examples described herein.

FIG. 5 illustrates another example user interface that provides toolsfor device-driven management using components of the networkedenvironment, according to various examples described herein.

FIG. 6 illustrates another example user interface that provides toolsfor device-driven management using components of the networkedenvironment, according to various examples described herein.

FIG. 7 illustrates another example user interface that provides toolsfor device-driven management using components of the networkedenvironment, according to various examples described herein.

FIG. 8 illustrates another flowchart performed by components of thenetworked environment for device-driven management, according to variousexamples described herein.

FIG. 9 illustrates another flowchart performed by components of thenetworked environment for device-driven management, according to variousexamples described herein.

DETAILED DESCRIPTION

Disclosed are various approaches for handing and resolving conflictswhen implementing device management workflows on the client device. Manyenterprises allow employees to work in various locations includingtraditional workplaces, temporary or field workplaces, as well as fromhome. At the same time, the complexity of processes utilized forprotecting enterprise resources has increased, requiring higherbandwidth for the constant communication of managed devices with amanagement service. Personal devices can frequently lose networkconnectivity, causing security issues, management failures, and delays.Although many of these issues can be addressed usingclient-device-driven management workflows, unexpected errors can occurwhen a client device attempts to process or implement a workflow. Forexample, multiple workflows may depend on different versions of the samelibrary or application be installed, or workflows may attempt to beginor continue execution during prohibited periods of time. Accordingly,various embodiments of the present disclosure improve the implementationof client-device-driven management workflows by handling conflictsbetween workflows in a manner that minimizes adverse impacts on theclient device.

In the following discussion, a general description of the system and itscomponents is provided, followed by a discussion of the operation of thesame. Although the following discussion provides illustrative examplesof the operation of various components of the present disclosure, theuse of the following illustrative examples does not exclude otherimplementations that are consistent with the principals disclosed by thefollowing illustrative examples.

With reference to FIG. 1, shown is a network environment 100 accordingto various embodiments. The network environment 100 can include acomputing environment 103 and one or more client devices 106. Thecomputing environment 103 and the client device(s) 106 can be in datacommunication with each other via a network 111. In the networkenvironment 100, the computing environment 103 and the client device(s)106 can communicate with or among each other over the network 111 usingone or more network transfer protocols or interconnect frameworks, suchas the hypertext transfer protocol (HTTP), simple object access protocol(SOAP), representational state transfer (REST), real-time transportprotocol (RTP), real time streaming protocol (RTSP), real time messagingprotocol (RTMP), user datagram protocol (UDP), internet protocol (IP),transmission control protocol (TCP), other protocols and interconnectframeworks, and combinations thereof.

The client devices 106 are representative of one or more client devices.Each client device 106 can be embodied as any computing device,processing circuit, or processor based device or system, including thosein the form of a desktop computer, a laptop computer, a tablet computer,a personal digital assistant, a cellular telephone, a wearable computingdevice, or a set-top box, among other example computing devices andsystems. Depending upon its primary purpose or function, for example,the client devices 106 can include various peripheral devices orcomponents. The peripheral devices can include input or communicationsdevices or modules, such as keyboards, keypads, touch pads, touchscreens, microphones, cameras, wireless communications modules (e.g.,infra-red, WI-FI, or BLUETOOTHS), buttons, switches, or sensors. Theperipheral devices can also include a display, indicator lights,speakers, global positioning system (GPS) circuitry, accelerometers,gyroscopes, or other peripheral devices depending upon the primarypurpose or function of the client devices 106. The client device 106 canalso include one or more displays 107, such as liquid crystal displays(LCDs), gas plasma-based flat panel displays, organic light emittingdiode (OLED) displays, electrophoretic ink (“E-ink”) displays,projectors, or other types of display devices. In some instances, thedisplay 107 can be a component of the client device 106 or can beconnected to the client device 106 through a wired or wirelessconnection. The client device 106 can also be configured to render auser interface 108 on the display for an application executed by theclient device 106. Examples of user interfaces 108 include web pages,application screens, and other graphical user interfaces (GUIs) or textuser interfaces (TUIs).

The network 111 can include wide area networks (WANs), local areanetworks (LANs), personal area networks (PANs), or a combinationthereof. These networks can include wired or wireless components or acombination thereof. Wired networks can include Ethernet networks, cablenetworks, fiber optic networks, and telephone networks such as dial-up,digital subscriber line (DSL), and integrated services digital network(ISDN) networks. Wireless networks can include cellular networks,satellite networks, Institute of Electrical and Electronic Engineers(IEEE) 802.11 wireless networks (i.e., Wi-FI®), BLUETOOTH® networks,microwave transmission networks, as well as other networks relying onradio broadcasts. The network 11 can also include a combination of twoor more networks 111. Examples of networks 111 can include the Internet,intranets, extranets, virtual private networks (VPNs), and similarnetworks.

The computing environment 103 can include one or more computing devicesthat include a processor, a memory, and/or a network interface. Forexample, the computing devices can be configured to perform computationson behalf of other computing devices or applications. As anotherexample, such computing devices can host and/or provide content to othercomputing devices in response to requests for content.

Moreover, the computing environment 103 can employ a plurality ofcomputing devices that can be arranged in one or more server banks orcomputer banks or other arrangements. Such computing devices can belocated in a single installation or can be distributed among manydifferent geographical locations. For example, the computing environment103 can include a plurality of computing devices that together caninclude a hosted computing resource, a grid computing resource or anyother distributed computing arrangement. In some cases, the computingenvironment 103 can correspond to an elastic computing resource wherethe allotted capacity of processing, network, storage, or othercomputing-related resources can vary over time.

The computing environment 103 can operate as an environment for mobiledevice management or a Unified Endpoint Management (UEM) platform thatcan manage the client devices 106, in that context, the computingenvironment 103 can includes a data store 110.

The computing environment 103 can also execute a management service 120.The management service 120 can generate a management console 121 thatincludes a user interface through which an administrator or other usercan manage client devices 106 that are enrolled with the managementservice 120. The administrator can access the management console 121using a client device 106. An identity provider 122 can be hosted usingthe computing environment 103 or can be used as a network service 109 inconjunction with the management service 120. The data store 110 includesareas in memory for the storage of device data 125, user data 127,enterprise resources 129, policies 131, profiles 132, configurations133, baselines 134, and other compliance rules. The data store 110 canalso include workflow objects 135, comprehensiveness definitions 137,and device-driven management workflows 139, among other types of data.The management service 120 can operate as a UEM platform that can manageclient devices 106 that are enrolled as managed devices with themanagement service 120. The management service 120 and the managementconsole 121 can be accessible over a public wide area network (WAN) suchas the Internet.

Device data 125 can represent information about client devices 106 thatare enrolled as managed devices with the management service 120. Thedevice data 125 can include a device identifier, certificates associatedwith the client device 106, a user identifier identifying the useraccount with which the device is linked, authentication tokens providedby the identity provider 122 to the client device 106, configurationprofiles and compliance policies 131 assigned to the client device 106,and other information regarding management of the client device 106 asan enrolled device. The device data 125 can also include a last-knowncompliance status associated with a managed client device 106. Thecompliance status can identify which compliance rules the client device106 or a user account linked to the client device 106 has violated. Forexample, the client device 106 may have been taken outside of aspecified geofence defined for the client device 106. The device data125 can also indicate a device type and a platform of the client device106. The device type can include desktop-type device, mobile-typedevice, tablet-type device, and the like. Device type can also refer toa device model or serial number. The platform of the client device 106can be an indication of an operating system 143 such as Windows® 10,macOS®, iOS®, Android®, as well as other versions of the operatingsystem 143.

User data 127 represents information about users who have user accountswith the management service 120 or an enterprise that uses themanagement service 120. These users can also have one or more clientdevices 106 that are enrolled as managed devices with the managementservice 120. User data 127 can include authentication data, andinformation about network services with which the user is assigned anaccount. The user data 127 can include a user account associates a useridentifier and one or more device identifiers for client devices 106.

The management service 120 can enroll several client devices 106 formobile device management services. To begin enrollment, the managementservice 120 can identify and authenticate one of the client devices 106and store data related to the client device 106 in the device data 125for later reference. In some cases, the management service 120 (or amanagement agent 145, an application 147, or another component executingon the client device 106) can also be registered as a deviceadministrator (at least in part) of the client device 106, permittingthe management service 120 to configure and manage certain operatingaspects of the client device 106.

Once a client device 106 is enrolled for device management by themanagement service 120, the management service 120 can providedevice-driven management workflows 139 for implementation on the clientdevice 106. The device-driven management workflows 139 can enforcepolicies 131, profiles 132, configurations 133, security baselines 134,and other compliance rules. The device-driven management workflows 139can also deploy enterprise resources 129, such as applications 147, dataresources, and access to network services 109 that are federated withthe identity provider 122.

The management service 120 can also maintain individual and groupcommand queues 123 for the client device 106. A client device 106 canperiodically check in and retrieve commands from the command queue 123.The management service 120 can also transmit a check-in notification tothe client device 106 that includes instructions to check in. Thecheck-in notification can be transmitted using a push notificationservice or another notification service, and the client device 106 cancheck in based on the notification. The management service 120 canprovide the device-driven management workflows 139 by placing, in acommand queue 123 for the client device 106, a command to execute thedevice-driven management workflow 139. The client device 106 can checkin, retrieve the command, and download the device-driven managementworkflow 139 from a location specified by the command. Once received,the device-driven management workflow 139 can be implemented by theclient device 106 without checking in with the command queue 123,including in scenarios where the client device 106 lacks a connectionwith the network 111 or otherwise lacks access to the command queue 123.

The management service 120 can also include, in the command queue 123, acommand to provide states 149, completion statuses, and other statusdata associated with execution of the device-driven management workflow139. The client device 106 can maintain a log of states 149, completionstatuses, and other workflow status data regarding execution of thedevice-driven management workflow 139. The client device 106 can checkin, retrieve the command to provide status data, and transmit the states149, completion statuses, and other specified information from the log.In other examples, the management agent 145 can transmit this data tothe management service 120 periodically, on a schedule, and at specifiedpoints in the device-driven management workflows 139. The managementservice 120 can identify success or failure of a portion of thedevice-driven management workflow 139 based on the states 149 and otherinformation received.

A device-driven management workflow 139 can specify one or more actions140 to be performed in order to enforce policies 131, profile 132,configurations 133, and/or security baselines 134 or to deployenterprise resources 129, such as applications 147, data resources, andaccess to network services 109 that are federated with the identityprovider 122. In some implementations, a device-driven managementworkflow 139 could be implemented as a state machine that specifies asequence or series of tasks 140 to be performed based on the currentstate or states of the of the client device 106.

Each task 140 can represent an action to be performed by the clientdevice 106 as part of a series or sequence of tasks 140 defined by thedevice-driven management workflow 139, where performance of the task 140can be based at least on part on the current or previous state 149 orstates 149 of the client device 106. Tasks 140 can be defined by using astate machine language (e.g., Amazon States Language) to specify a taskor action to be performed based at least in part on the current orprevious state 149 of the client device 106. The use of the statemachine language can also specify the dependencies of the task 140(e.g., other tasks 140 which must be performed prior to performance ofthe defined task 140). In addition, the device-driven managementworkflow 139 can also be represented using a state machine language,such as Amazon State Language.

Individual tasks 140 can also specify one or more dependencies 141. Adependency 141 can represent a resource (e.g., a configuration file,application, library, etc.) that an individual task 140 of adevice-driven management workflow 139 requires in order to complete orbe completed. For example, if a task 140 were to install an application147 on a client device 106, the dependency could specify a specificversion or minimum version of a library that the application 147requires or a specific version or minimum version of the application 147to be installed. For instance, the dependency 141 could specify that atleast version 8.0 or higher of the specified library be installed orthat at least version 10.0 or higher of the specified application 147 beinstalled. Multiple device-driven management workflows 139 could havetasks 140 that share a common dependency 141, such as the sameconfiguration file, library or application 147 being installed on theclient device 106.

One or more time windows 142 may also be stored in the data store 110. Atime window 142 can represent a period of time that matches one or moreclassifications specified by an administrator using the managementconsole 121. Time windows 142 can represent a single block of time(e.g., a three-hour block from noon to 3:00 p.m. on Friday the 13th), ora recurring block of time (e.g., a 10-hour block of time from 8:00 a.m.to 6:00 p.m. every weekday). Time windows 142 can also be assigned toone or more classes or classifications. For example, a time window 142could be classified as “business hours,” “maintenance period,” etc.

Workflow objects 135 can include a set of graphical tools that can beused in the management console 121 to form device-driven managementworkflows 139. Each workflow object 135 can include instructionsformatted using a particular syntax, such as a state machine language(e.g., Amazon State Language). Since the workflow objects 135 can beused to form the device-driven management workflows 139, eachdevice-driven management workflow 139 can also use the syntax of theworkflow objects 135. Workflow objects 135 can include instructions thatinstall payloads, policies 131, profiles 132, configurations 133,baselines 134, and other enterprise resources 129. Workflow objects 135can include instructions for evaluation of device states 149, policies131, profiles 132, configurations 133, baselines 134, and device statedefinitions 155 such as evaluation of device-specific risk levels for aclient device 106 based on its states 149. The workflow objects 135 canalso include entry points that specify a group of client devices 106,for example, according to user group, device type, platform, otherdevice data 125, and other user data 127.

The workflow objects 135 can also include connector workflow objects 135between other workflow objects 135. Connector workflow objects 135 canspecify conditions and states 149 under which a branch corresponding tothat connector is to be implemented. Connector workflow objects 135 canextend from the evaluation workflow object 135. Evaluation workflowobjects 135 can include if, while, for, AND, OR, NAND, NOR, and otherconditions. The states 149 for respective branch connectors from anif-evaluation workflow object 135 can be mutually exclusive from states149 for other branch connectors. Alternatively, the states 149 forbranch connectors from an if-evaluation workflow object 135 can beevaluated in an order specified by the if-evaluation workflow object135.

Comprehensiveness definitions 137 can identify a set of device states149 or device conditions that a device-driven management workflow 139can include in order to be considered comprehensive. In some cases, acomprehensiveness definition 137 can be generated for a particularenterprise based on the known device data 125 and user data 127 for theenterprise. In other cases, a comprehensiveness definition 137 can begenerated for a particular user group or another logical grouping ofclient devices 106 using a filtered subset of the device data 125 anduser data 127 for that logical grouping of client devices 106.

States 149 are a reference to the current or previous state of theclient device 106 according to one or more criteria. The state 149 orstates 149 of the client device 106 can also change in response to themanagement agent 145 implementing, processing, or otherwise executingone or more tasks 140 specified by a device-driven management workflow139. For example, as the management agent 145 installs or updatesapplications 147 on the client device 106 as specified by a devicemanagement workflow 139, the state 149 of the client device 106 wouldchange to reflect the presence of the applications 147 as well as theircurrent versions and any dependencies.

States 149 can include conditions on the client device 106 such asplatform of the client device 106, a type of the client device 106, ageolocation of the client device 106, a public or private network towhich the client device 106 is communicatively connected, a user groupassociated with the client device 106, applications 147 that areinstalled on the client device 106, settings of the client device 106,and other device conditions. The following examples set forth a numberof illustrative examples of different types of data that may be referredto or represented by the state 149 of the client device 106. However, itis understood that the following examples are not intended to limit thescope of the state 149 of the client device 106. For example, the state149 of the client device 106 could refer to or represent a current orprevious platform or operating system 143 of the client device 106,including a current or previous version of the platform or operatingsystem 143. The state 149 could also refer to or represent a current orprevious sensor value or range of sensor values detected by a sensor ofthe client device 106. The state 149 could also refer to or representwhether an application 147 is installed on the client device 106, or thespecific version of the application 147 installed on the client device106. The state 149 could also refer to or represent whether a script hasbeen executed on the client device 106, the version of the script thatwas executed, or the result of the execution of the script. The state149 could also refer to or represent whether a file is stored on theclient device 106, or the version of the file stored on the clientdevice 106. The state 149 could also refer to or represent a total,used, or available amount of storage, memory, compute, or networkbandwidth for the client device 106. The state 149 could also refer toor represent a current network address or IP address of the clientdevice 106. The state 149 could also refer to or represent a geolocationor physical location of the client device 106. The state 149 could alsorefer to or represent a model or type of the client device 106.

The management service 120 can analyze the device data 125 and the userdata 127 for a particular logical grouping of client devices 106 andgenerate a comprehensiveness definition 137 that includes a superset ofconditions including platforms, states 149, user groups, networks,geolocations, and applications 147 for the logical grouping of clientdevices 106. The management service 120 can identify a logical groupingof client devices 106 relevant to a device-driven management workflow139.

Comprehensiveness definition 137 can be static or dynamic. For example,a user can access the management console 121 and begin designing adevice-driven management workflow 139. The management service 120 cananalyze the workflow objects 135 of the device driven workflow 139 anddetermine that the device-driven management workflow 139 is limited to aparticular user group, a particular operating system, or both. Themanagement service 120 can identify a logical grouping of client devices106 based on the current limitations of the device-driven managementworkflow 139. The management service 120 can generate a dynamicworkflow-specific comprehensiveness definition 137 that includes asuperset of conditions including platforms, states 149, user groups,networks, geolocations, and applications 147 limited to theworkflow-specific logical grouping of client devices 106. The managementconsole 121 can provide recommendations for the device-driven managementworkflow 139 based on the workflow-specific comprehensiveness definition137.

In another example, the user can select a static comprehensivenessdefinition 137 that includes conditions including platforms, states 149,user groups, networks, geolocations, and applications 147 forcomprehensive coverage of client device 106. Even if the device-drivenworkflow 139 is currently limited to devices that do not correspond tothe static comprehensiveness definition 137, the management console 121can provide recommendations for the device-driven management workflow139 based on the broader set of conditions of the staticcomprehensiveness definition 137. Recommendations can identify locationssuch as workflow objects 135 and branching locations where a conditioncan be added to the device-driven management workflow 139. Thecomprehensiveness definitions 137 can be used by the management console121 to provide recommendations for device conditions, states 149,applications 147, and enterprise resources 129 to include in aparticular device-driven management workflow 139.

Unlike traditional management workflows that are directed by themanagement service 120, the device-driven management workflows 139enable an end user's client device 106 to direct deployment operationsto install policies 131, profiles 132, configurations 133, securitybaselines 134, and other compliance rules, as well as applications 147,certificates, and other enterprise resources 129. To this end,device-driven management workflows 139 can include a branching sequenceof instructions that branches based on states 149 that are evaluated onthe end user's client device 106. States 149 can be evaluated by amanagement agent 145 based on instructions in the device-drivenmanagement workflows 139 once delivered. As a result, the path that isultimately executed for a single device-driven management workflow 139can be different for different client devices 106 that include differentstates 149.

The management service 120 can also provide a management console 121 asan engine and console interface for device management of the clientdevices 106. An information technology administrator or user, forexample, can view, administer, and update client-device drivenmanagement workflows 139 using the management console 121. Theclient-device driven management workflows 139 can be deployed ortransmitted to a set of the client devices 106 to install and enforcepolicies 131, profiles 132, configurations 133, security baselines 134,and other compliance rules. The client-device driven managementworkflows 139 can also install applications 147, and other componentsthat enable access to network services 109 and enterprise resources 129.The compliance rules can be collectively administered for several of theclient devices 106 by organizing the client devices 106 into severaldifferent groups or categories of devices according to organizational,platform, and other factors.

The management console 121 can include a workflow creation userinterface area. The workflow creation user interface area can include adrag-and-drop canvas user interface area that shows the workflow objects135 of a device-driven management workflow 139 in a workflow view; aprogramming language user interface area that shows the workflow objects135 of a device-driven management workflow 139 in text instructions orcode form; or a list or tree view that shows the workflow objects 135 ofa device-driven management workflow 139.

The identity provider 122 can provide single sign-on or identitymanagement capabilities for access to enterprise resources 129 throughthe management service 120 as well as network services 109. The identityprovider 122 can allow users to authenticate his or her identity toobtain an authentication token that can be provided to a network service109. The identity provider 122 can utilize OAuth, security assertionmark-up language (SAML), or other single sign-on methodologies. Theidentity provider 122 and management service 120 can communicate so thatthe management service 120 can revoke or authorize access to variousservices for users in the enterprise based on status of a client device106 assigned to the user. The identity provider 122 can also rely onuser data 127 in the data store 110. In some examples, the identityprovider 122 can rely upon a separate source of user data in a separatedata store.

The network service 109 can be embodied as one or more computers,computing devices, or computing systems. Like the computing environment103, the network service 109 can include one or more computing devicesarranged, for example, in one or more server or computer banks. Thecomputing device or devices can be located at a single installation siteor distributed among different geographical locations. The networkservice 109 can include a plurality of computing devices that togetherembody a hosted computing resource, a grid computing resource, or otherdistributed computing arrangement. The network service 109 can also beembodied, in part, as certain functional or logical (e.g.,computer-readable instruction) elements or modules as described herein.The network service 109 can be provided by an enterprise to its usersand can include first- and third-party network services 109 with respectto the management service 120. For example, a network service 109 caninclude an optional service from a provider of the management service120 or can be a third-party network service 109. The managementworkflows 153 and the device state definitions 155 from a third-partynetwork service 109 can be referred to as third-party managementworkflows 153 and third-party device state definitions 155. The networkservice 109 can federate its authentication for users of the enterpriseto the identity provider 122. The network service 109 can be accessibleover the Internet or another public WAN.

An example client device 106 can be enrolled by the management service120 for device management. A management agent 145 can be installed on aclient device 106 to locally manage the device using device-drivenmanagement workflows 139 that are provided by the management service120. The management agent 145 can be installed with elevated privilegesor be effectuated through operating system APMs to manage the clientdevice 106 on behalf of the management service 120. The management agent145 can have the authority to manage data on the client device 106,install, remove, or disable certain applications, or installconfiguration profiles, such as VPN certificates, Wi-Fi profiles, emailprofiles, etc.

The management agent 145 can also have the authority to enable ordisable certain hardware features of the client device 106 that arespecified for a particular branch of a device-driven management workflow139. The management agent 145 can also place the device into differenthardware modes, such as airplane mode, silent mode, do-not-disturb mode,or other modes supported by the client device 106.

The management agent 145 can perform device-driven management workflows139 to alter operation of the client device 106 in response to changesin states 149 that are detected on the client device 106. The managementagent 145, in one instance, can periodically poll the operating system143, a data store, or other software and hardware components of theclient device 106 to identify states 149 that are indicated in adevice-driven management workflow 139.

The device-driven management workflows 139 can include appropriatecommands in response to certain states 149. Commands can includegenerating a notification on the client device 106, sending anotification to an administrator, sending a notification and othercompliance data to the management service 120, changing a non-compliantstate 149 to a compliant state 149, deleting applications 147 and otherenterprise resources, ending a SSO session with the identity provider,removing access to enterprise resources, and other management actions onthe client device 106. In one example, the management agent 145 candetect that the client device 106 is out of compliance with respect to acompliance rule indicated in device-driven management workflows 139 andmight instruct the management agent 145 to restrict a hardware featureof the client device 106, delete data from the client device 106, ordisable certain applications on the client device 106. The managementagent 145 can also take other variations of management actions on theclient device 106 as directed by the device-driven management workflows139.

As part of the enrollment process, the management service 120 and/ormanagement agent 145 can be registered as a device administrator of theclient device 106, permitting the management service 120 and/ormanagement agent 145 to manage certain operating aspects of the clientdevice 106. In either case, the management service 120 can remotelyconfigure the client device 106 by interacting with the management agent145. The device-driven management workflows 139 can also indicatevarious applications 147 and software components to install on theclient device 106. Such software components can include, for example,applications, resources, libraries, drivers, device configurations, orother related components. The device-driven management workflows 139 canalso indicate network locations where the software components can bedownloaded for installation. The device-driven management workflows 139can also indicate to download and install compliance rules and instructthe management agent 145 and the operating system 143 of the clientdevice 106 to enforce the compliance rules.

The client device 106 can also store a workflow queue 150. The workflowqueue 150 can be used to store device-driven management workflows 139retrieved from the management service 120 for later implementation orexecution by the management agent 145. In some implementations,device-driven management workflows 139 could be performed in the orderthey are stored in the workflow queue 150. Accordingly, the managementagent 145 could evaluate individual device-driven management workflows139 to identify common dependencies 141 for individual tasks 140 of thedevice-driven management workflows 139. The identification of commondependencies 141 would allow for the management agent 145 to resolve acommon dependency 141 once for multiple device-driven managementworkflows 139 compared to repeating, resolving, or reimplementing thecommon dependencies 141 multiple times when each separate device-drivenmanagement workflow 139 is processed or executed.

Common dependencies 141 are those dependencies 141 which may be sharedby multiple tasks 140. Individual tasks 140 that share a commondependency 141 could be components or steps of separate device-drivemanagement workflows 139. For example, if two device-driven managementworkflows 139 had a task 140 to install an application 147 or a library,the common dependency 141 would be installation of the application 147or library. Where a common dependency 141 involves multiple versions ofa resource (e.g., configuration file, application 147, library, etc.), aversion hierarchy 151 can be can created by the management agent 145 totrack and resolve which version of the common dependency 141 would bethe most appropriate version to resolve the common dependency 141.

The version hierarchy 151 can represent a hierarchy of identified commondependencies 141 according to one or more criteria. For example, ifseveral tasks 140 specify a dependency that a particular configurationfile, library, or application 147 be installed, the version hierarchy151 could represent which versions of the configuration file, library,or application 147 are specified by individual tasks 140. Moreover, theversion hierarchy 151 could track which workflows are dependent on thehighest or most recent version of the configuration file, library, orapplication 147, and which workflows are dependent on a lower or olderversion of the configuration file, library, or application 147. In someimplementations, each dependency 141 for a task 140 in a device-drivenmanagement workflow 139 could have an associated version hierarchy 151.In other implementations, only dependencies 141 that are shared acrossor common to multiple tasks 140 or device-driven management workflows139 could have an associated version hierarchy 151.

The management workflows 153 can include enterprise management workflows153 for an enterprise employing the management service 120. The devicestate definitions 155 can include device state definitions 155 andenterprise device state definitions 155. The network services 109 caninclude previous or legacy management services, community network siteswhere management workflows 153 and device state definitions 155 can bepublicly posted and accessed, private servers to which an enterprise hasaccess, and other services.

The management service 120 can include network service integrations 138that enable the management service 120 to identify and retrieve first-and third-party resources including the management workflows 153 anddevice state definitions 155. The management service 120 can displaythese resources in the management console 121. The management service120 can also allow management workflows 153 and device state definitions155 to be imported and translated into device-driven managementworkflows 139. A device state definition 155 can be reformatted using aparticular syntax to form a new or modified workflow object 135, or adevice-driven management workflow 139 capable of assessing the devicestate definitions 155 on a client device 106. A management workflow 153can be retrieved and reformatted into a device-driven managementworkflow 139 that is expressed using a set of workflow objects 135.

FIG. 2 shows a flowchart 200 performed by components of the networkedenvironment 100. Specifically, the flowchart 200 describes how themanagement service 120 provides tools that can import the resources fromnetwork services 109 and translate them into workflow objects 135 anddevice-driven management workflows 139. While the flowchart 200 isdescribed as performed by the management service 120, it can also beconsidered functionality performed by the management console 121.Certain functionality described for the flowchart 200 can also beperformed by other components of the networked environment 100.Segmentation and ordering indicated in the flowchart 200 is for examplepurposes only. The functionality described for a particular step can beperformed in any order relative to the other steps described.

At step 203, the management service 120 can generate a managementconsole 121 that includes a workflow creation user interface area and atool panel that includes a set of workflow objects 135. The workflowcreation user interface area can include a drag-and-drop canvas userinterface area that shows the workflow objects 135 of a device-drivenmanagement workflow 139 in a workflow view. The workflow objects 135 canbe selected, placed, moved, and connected in the drag-and-drop canvas toform device-driven management workflows 139. The workflow objects 135can be selected, placed, moved, and connected in the drag-and-dropcanvas to form device-driven management workflows 139. Other views andmanipulation types can also be used as described.

Device-driven management workflows 139 can include a branching sequenceof instructions that branches based on states 149 that are evaluated onthe end user's client device 106. A path that is ultimately performedand executed for a single device-driven management workflow 139 can bedifferent for different client devices 106 based on the particularstates 149 of the devices.

The workflow objects 135 can include instructions that can be performedby the management agent 145, as well as a graphical representation thatcan be manipulated in the management console 121 to form device-drivenmanagement workflows 139. Each workflow object 135 can be represented byan icon or another graphical representation. Workflow objects 135 caninclude instructions that install payloads, policies 131, profiles 132,configurations 133, baselines 134, and other enterprise resources 129.Workflow objects 135 can include instructions that evaluate devicestates 149, policies 131, profiles 132, configurations 133, baselines134, and device state definitions 155 such as evaluation ofdevice-specific risk levels for a client device 106 based on its states149.

The workflow objects 135 can also include entry points. Entry points canbe the starting point for a device-driven management workflow 139.Different types of workflows can have different types of entry points.For example, a provisioning device-driven management workflow 139 canhave an entry point that specifies a group of client devices 106according to user group, device type, platform, other device data 125,and other user data 127. A smart application device-driven managementworkflow 139 can have an entry point that specifies an applicationworkflow object 135 that triggers its execution. A state evaluationdevice-driven management workflow 139 can have an entry point thatspecifies to periodically poll for a state 149. A state evaluationdevice-driven management workflow 139 can be deployed as an enforcementmechanism that performs a branching set of instructions based onadherence to or violation of policies 131, profiles 132, baselines 134,required or prohibited applications 147, and other states 149.

In step 206, the management service 120 can retrieve resources from anetwork service 109. The management service 120 can include networkservice integrations 138 that enable communication with the networkservices 120. For example, the network service integrations 138 caninclude components that specify a network address of a network service109 where resources including management workflows 153 and device statedefinitions 155 can be retrieved. The management service 120 can parsethe text of a management workflow 153 or device state definitions 155 todetect a syntax of the resource. The management service 120 can thenidentify predetermined translation instructions and translate theresource into different syntax in order to generate a workflow object135 or device-driven management workflow 139.

In some cases, the network service 109 can include a public websitewhere the public can post management workflows 153 and device statedefinitions 155. In other examples, the network service 109 can includea private website where an enterprise can store management workflows 153and device state definitions 155. The management service 120 can includecredentials, certificates, and other components that enable themanagement service 120 to authenticate with the network service 120. Themanagement service 120 can also allow a user or administrator to log inwith a single sign on credential and use the identity provider 122 toauthenticate with multiple network services 120.

In step 209, the management service 120 can identify a user-selection ofa network-retrieved management resource such as a management workflow153 or a device state definition 155 from the management console 121.The management service 120 can generate the management console 121 toinclude user-selectable interface elements for the management workflows153 and device state definitions 155 that are retrieved from the networkservice 120. The management service 120 can identify a user selection ofan interface element for a management workflow 153 or device statedefinition 155.

In step 212, the management service 120 can translate the managementworkflow 153 into a device-driven management workflow 139. Themanagement service 120 can generate a device-driven management workflow139 that conforms to the set of workflow objects 135 provided by themanagement console 121. The device-driven management workflow 139 can bea translated version of the management workflow 153. While the examplediscusses translation of a management workflow 153, the managementservice 120 can also retrieve a device state definition 155 andtranslate it into a new workflow object 135 that matches a syntax of theset of workflow objects 135. While translation is indicated after theselection of the management resource, the management service 120 canalso automatically translate the management resource before showing itin the management console 121.

In step 215, the management service 120 can include the translatedversion of the management workflow 153 in the drag-and-drop or canvasuser interface area of the management console 121. The user can click orclick-and-drag the translated version of the management workflow 153from an imported resources area, or another tool user interface elementof the management console 121. The translated version of the managementworkflow 153 can then be shown in the drag-and-drop or canvas userinterface area. The user can then edit workflow objects 135 of thetranslated version of the management workflow 153 components through themanagement console 121.

In step 218, the management service 120 can transmit the translatedversion of the management workflow 153 to client devices 106. Forexample, the management service 120 could save the translated version ofthe management workflow 153 to a command queue 123. At periodicintervals, the management agent 145 could send a request to themanagement service 120 for any objects (e.g., translated versions of themanagement workflow 153) stored in the command queue 123 for the clientdevice 106, and the management service 120 could provide them inresponse. In some implementations, the management agent 145 coulddirectly retrieve objects stored in the command queue 123 withoutsending a request to the management service 120.

Once received, the client devices 106 can evaluate states 149 andperform a client-device-specific path or route through theclient-device-driven management workflow 139 that is based on thetranslated version of the management workflow 153. Alternatively, themanagement service 120 can save the device-driven management workflow139 for later deployment. The device-driven management workflow 139 canperform any of the functionality discussed. The device-driven managementworkflow 139 can also be saved as a smart resource workflow object 135or another multi-step workflow object 135 for use in other device-drivenmanagement workflows 139. A smart resource workflow object 135 oranother multi-step workflow object 135 can correspond to a device-drivenmanagement workflow 139 that can be represented by a single icon orgraphic in another device-driven management workflows 139.

A smart resource workflow object 135 can refer to a device-drivenmanagement workflow 139 for comprehensive or universal deployment ofenterprise resources 129 such as applications 147, scripts, databases,or files for a set of conditions specified by a comprehensivenessdefinition 137. As a result, the smart resource workflow object 135 canbe used in other device-driven management workflows 139. For example, asingle smart resource workflow object 135 can be used to deploy multipledifferent versions of an application 147 or a script depending on aplatform or operating system 143 of a client device 106. A single smartresource workflow object 135 can be used to install or provide access todifferent databases or files based on a user group or security state 149of the client device 106.

FIG. 3 shows a flowchart 300 performed by components of the networkedenvironment 100. Specifically, the flowchart 300 describes how themanagement service 120 provides tools that can create universal orcomprehensive device-driven management workflows 139. This can includeuniversal or smart applications as well as device-driven managementworkflows 139 for deployment or installation of enterprise resources129, evaluation and enforcement of compliance rules on the client device106, and other purposes. While the flowchart 300 is described asperformed by the management service 120, it can also be consideredfunctionality performed by the management console 121. Certainfunctionality described for the flowchart 300 can also be performed byother components of the networked environment 100. Segmentation andordering indicated in the flowchart 300 is for example purposes only.The functionality described for a particular step can be performed inany order relative to the other steps described.

At step 303, the management service 120 can generate a managementconsole 121 that includes a workflow creation user interface area and atool panel that includes a set of workflow objects 135. The workflowcreation user interface area can include a drag-and-drop canvas userinterface area that shows the workflow objects 135 of a device-drivenmanagement workflow 139 in a workflow view. The workflow objects 135 canbe selected, placed, moved, and connected in the drag-and-drop canvas toform device-driven management workflows 139. Other views andmanipulation types can also be used as described.

At step 306, the management service 120 can identify a comprehensivenessdefinition 137 to use for a device-driven management workflow 139 shownin the workflow creation user interface area. For example, themanagement service 120 can analyze the workflow objects 135 of thedevice-driven management workflow 139 and identify a logical grouping ofclient devices 106 based on current limitations of the device-drivenmanagement workflow 139. The management service 120 can generate adynamic workflow-specific comprehensiveness definition 137 that includesa superset of conditions including platforms, states 149, user groups,networks, geolocations, and applications 147 limited to theworkflow-specific logical grouping of client devices 106. Alternatively,the user can select a predetermined or static comprehensivenessdefinition 137.

In step 309, the management service 120 can define a device-drivenmanagement workflow 139 based on user interactions identified throughthe workflow creation user interface area of the management console 121.For example, a user can drag one or more workflow objects 135 into theworkflow creation user interface area and link them using connectors.The user can also select workflow objects 135, including the connectors,in order to edit specifications of the various workflow objects 135. Theuser can also incorporate management workflows 153, device statedefinitions 155, and modified versions of these management resourcesinto the device-driven management workflow 139.

In step 312, the management service 120 can determine whether thedevice-driven management workflow 139 is comprehensive. For example, themanagement service 120 can compare the workflow objects 135 of thedevice-driven management workflow 139 to comprehensiveness definition137. The comprehensiveness definition 137 can be a staticcomprehensiveness definition 137 or a dynamic comprehensivenessdefinition 137 that changes based on a detected set of limitationsapplicable to all paths through the device-driven management workflow139. If the device-driven management workflow 139 includes all or athreshold percentage or amount of the conditions specified in thecomprehensiveness definition 137, then the device-driven managementworkflow 139 can be considered comprehensive and the process can proceedto step 321. Otherwise, the device-driven management workflow 139 can beconsidered not comprehensive, and the process can move to step 315.

In step 315, the management service 120 can generate a notification thatthe device-driven management workflow 139 lacks instructions for acondition or device state 149 that is specified by the comprehensivenessdefinition 137. For example, the device-driven management workflow 139can lack a path corresponding to a network condition (e.g., trusted,untrusted), geolocation, platform, or other condition. The device-drivenmanagement workflow 139 can lack instructions to ensure installation ofa certain application 147 or another enterprise resource 129 that isspecified by the comprehensiveness definition 137. The notification canbe included in a pop-up user interface element or another informationalor administrative user interface panel of the management console 121.

In step 318, the management service 120 can provide a workflow object135 that includes the device state 149 that is specified by thecomprehensiveness definition 137. For example, the management console121 can include a pop-up user interface element or another userinterface panel that shows the workflow object 135 that includes thedevice state 149. The workflow object 135 can also be highlighted orotherwise graphically emphasized in a toolset or another area of themanagement console 121. A user can select the workflow object 135 whereshown in the management console 121 and incorporate the workflow object135 into device-driven management workflow 139. Alternatively, themanagement service 120 can show the state 149 in a pop-up user interfaceelement or another user interface panel, and the user can select ormanipulate the state 149 to incorporate the state 149 into an existingworkflow object 135.

In step 321, the management service 120 can determine whether to deploythe device-driven management workflow 139. For example, the managementconsole 121 can include a user interface element through which a usercan indicate to deploy the device-driven management workflow 139 to aset of client devices 106. If the device-driven management workflow 139is to be deployed, then the process can proceed to step 324. Otherwisethe process can proceed to step 303.

In step 324, the management service 120 can transmit the device-drivenmanagement workflow 139 to a set of client devices 106. This could bedone, for example, by placing the device-driven management workflow 139into one or more command queues 123 from which the client devices 106subsequently retrieve the device-driven management workflows 139. Theset of client devices 106 can correspond to a user group, a devicegroup, a platform-based group, or another logical grouping of clientdevices 106. The logical grouping of client devices 106 can be indicatedin an entry point workflow object 135 of the device-driven managementworkflow 139.

FIG. 4 shows an example user interface 108 of the management console121. The user interface can include tools for device-driven management.For example, the management console 121 can include a workflow creationarea 403, as well as a side panel 406 for options and configuration. Theworkflow creation area 403 can include a toolset selector 409, aninterface type selector 412, as well as a name or identifier 415 of adevice-driven management workflow 139.

The workflow creation area 403 can include a drag-and-drop canvas userinterface that shows the workflow objects 135 of a device-drivenmanagement workflow 139 in a graphical workflow view that includesicon-type or other graphical representations of workflow objects 135connected to one another using line-type connector workflow objects 135.Using the interface type selector 412, a user can change the workflowcreation area 403 to include a programming language user interface areathat shows the workflow objects 135 of a device-driven managementworkflow 139 in text instructions or code form; or a list or tree viewthat shows the workflow objects 135 of a device-driven managementworkflow 139. In some examples, the drag-and-drop canvas user interfacecan be in the workflow creation area 403, while the side panel 406includes the programming language or the tree view of the device-drivenmanagement workflow 139.

The toolset selector 409 can include, from left to right, a filter icon,an inventory icon, a commands icon, a groups icon, a connector icon, anetwork service integrations icon, among others. A user selection of thefilter icon can cause the management console 121 to show a toolsetfiltering element to filter the toolsets shown in the toolset selector409.

A user selection of the inventory icon can cause the management console121 to show an inventory toolset. The inventory toolset can includeworkflow objects 135 corresponding to enterprise resources 129 such asdatabases, certificates, files, scripts, and applications 147.

A user selection of the commands icon can cause the management console121 to show a commands toolset. The commands toolset can includeworkflow objects 135 corresponding to commands that can be performed byan operating system 143, an application 147, or other instructionsexecuted on the client device 106. For example, commands can include areboot command, a logout command, an enterprise wipe command thatremoves enterprise resources 129 from the client device 106, a commandto generate a local notification, a command to transmit a message, acommand to update data in a local or remote database, a command toperform an action using a network service 109 or the management service120, a command to set a host name of the client device 106, a command toset a wallpaper of the client device 106, and other commands.

A user selection of the groups icon can cause the management console 121to show a groups toolset. The groups toolset can include workflowobjects 135 corresponding to user groups, device groups, and otherlogical groupings of client devices 106. The groups toolset can be usedto modify workflow objects 135 in the device-driven management workflow139. For example, a group workflow object 135 can modify a connectorworkflow object 135, such as an entry point, a line connector, or acondition based on the specified group.

A user selection of the connectors icon can cause the management console121 to show a connectors toolset. The connectors toolset can includeworkflow objects 135 corresponding to connectors including entry points,line connectors, and conditions. Entry point workflow objects 135 can beused to start a device-driven management workflow 139. If thedevice-driven management workflow 139 is a complete standalone workflow,then the entry point can specify a specific client device 106, or a usergroup, a device group, or another logical grouping of client devices 106for the device-driven management workflow 139.

In this example, the toolset selector 409 indicates that the networkservice integrations icon is selected. The network service integrationstoolset 418 can show a number of icons corresponding to network serviceintegrations 138 with network services 109. The network serviceintegrations toolset 418 can provide an indicator of a number of networkservice integrations 138 that are currently set up. The example hereshows that there are six (6) network service integrations 138 currentlyconfigured to import management workflows 153, device state definitions155, and other first- and third-party management resources for adevice-driven management workflow 139.

Selection of a particular network service integration from the networkservice integrations toolset 418 can update the network serviceintegrations toolset 418 to show management workflows 153, device statedefinitions 155, and other management resources. Alternatively,selection of a particular network service integration from the networkservice integrations toolset 418 can update the side panel to showmanagement workflows 153, device state definitions 155, and othermanagement resources.

The network service integrations toolset 418 can also include a searchfunctionality and a filter functionality. For example, a user can selecta search icon to bring up a search element through which a user-enteredtextual search query can be entered. The management console 121 canupdate the network service integrations toolset 418 or the side panel406 to show network service integrations 138, management workflows 153,device state definitions 155, and other management resourcescorresponding to the query.

A user can select a filter icon of the network service integrationstoolset 418 to bring up a filtering element through which a set ofcategories can be user-selected. The management console 121 can updatethe network service integrations toolset 418 or the side panel 406 toshow network service integrations 138, management workflows 153, devicestate definitions 155, and other management resources corresponding tothe user-selected category.

FIG. 5 shows an example user interface 108 of the management console121. The user interface can include tools for device-driven management.For example, the management console 121 can include a workflow creationarea 403, a side panel 406, and other components as discussed.

The workflow creation area 403 can include a device-driven managementworkflow 139 that is created using workflow objects 135. The side panel406 can include a number of management resources that a user can selectfor inclusion in the workflow creation area 403 and the device-drivenmanagement workflow 139. The management resources can include devicestate definitions 155 and a management workflow 153, which can includefirst- and third-party management resources that are retrieved fromnetwork services 109 using network service integrations 138.

A user can manipulate a cursor, touchscreen, or other input device toselect the management workflow 153 “Flow_1” The user can click,click-and-drag, or otherwise select the management workflow 153 and addit to the workflow creation area 403 as a set of workflow objects 503 ofthe device-driven management workflow 139. The workflow object group 503can be a translated version of the management workflow 153 formatted asworkflow objects 135 as discussed. The user can then edit thedevice-driven management workflow 139. For example, the user can add oredit an entry point 506 to specify a logical grouping of client devices106 for the device-driven management workflow 139. The managementconsole 121 also includes a user interface element 509 that can beuser-manipulated to save, publish, or delete the device-drivenmanagement workflow 139. Publishing the device-driven managementworkflow 139 can involve transmitting the device-driven managementworkflow 139 to client devices 106 specified by the entry point 506.

The workflow object group 503 shows workflow objects 135 including anif-condition workflow object 135, an OS1 connector workflow object 135,and an OS2 connector workflow object 135, among others. When executed bya client device 106, the device-driven management workflow 139 or themanagement agent 145 can analyze states 149 to determine an operatingsystem 143 of the client device 106. If the operating system 143corresponds to that specified by the OS1 connector workflow object 135,then the branch of instructions corresponding to the OS1 connectorworkflow object 135 can be performed. If the operating system 143corresponds to that specified by the OS2 connector workflow object 135,then the branch of instructions corresponding to the OS2 connectorworkflow object 135 can be performed. As a result, the device-drivenmanagement workflow 139 includes a branching sequence of instructionsthat branches based on states 149 that are evaluated on the end user'sclient device 106.

As a nonlimiting example, the branch of instructions corresponding tothe OS1 connector workflow object 135 can install two configurations 133and a security baseline 134. The bounding box around the twoconfigurations 133 and the security baseline 134 can indicate that theseworkflow objects 135 are order agnostic, can be performed in any orderincluding with partial or total concurrence, simultaneously, orotherwise. Thereafter, the branch of instructions indicates to installfive payloads of data or other enterprise resources 129, andsubsequently install five applications 147. The branch of instructionscorresponding to the OS2 connector workflow object 135 can install threeconfigurations 133, subsequently install seven payloads, andsubsequently install four applications 147.

The management resources can also include risk levels and other devicestate definitions 155. The risk level definitions can be generated by anetwork service 109. In some examples, the risk level definitions can bemade in the same syntax of the workflow objects 135, and in otherexamples the management service 120 can translate a first- orthird-party syntax into a different syntax used by the workflow objects135 to create the new workflow objects 135.

Risk level definitions can be used to modify workflow objects 135 in thedevice-driven management workflow 139. For example, a risk leveldefinition workflow object 135 can modify a connector workflow object135, such as an entry point, a line connector, or a condition based onthe specified risk level definition. Risk level definitions can define aset of states 149 that are associated with that risk level. Whenexecuted on a client device 106 as part of a device-driven managementworkflow 139, the states 149 can be detected and compared to thosespecified by the risk level definition workflow object 135. The risklevel definitions can be initially generated by machine learning oranother method.

The risk level definitions can be periodically updated by the networkservice 109. However, the risk level definition workflow object 135 canspecify a network location where the states 149 specified by the risklevel definition can be updated to reflect changing security risks facedby client devices 106. The device-driven management workflow 139 can bedeployed to a client device 106, and the client device 106 can updatethe states 149 that trigger the risk level definition workflow object135. The management agent 145 can retrieve a risk level definitionperiodically and in response to a detected change of a state 149 of theclient device 106. This can be achieved without contacting themanagement service 120 for a new or updated device-driven managementworkflow 139. While discussed with respect to risk level definitions,any device state definition 155 can specify a network location of anetwork service 109 that enables the client device 106 to update aworkflow object 135 for that device state definition 155.

The management agent 145 can generate a risk score for the client device106 based on the states 149 and the risk level definition. In othercases, the management agent 145 can periodically transmit states 149 tothe network service 109 and can receive a risk score for the clientdevice 106. The management agent 145 can compare the risk score to therisk level to determine whether to perform a branch of the device-drivenmanagement workflow 139 that corresponds to the risk level.

The if-condition workflow object 135, the OS1 connector workflow object135, the OS2 connector workflow object 135, and other workflow objects135 can be edited based on the device state definitions 155. Forexample, a device state definition 155, “Risk_Lvl_1” can be used tomodify the OS1 connector workflow object 135 to replace a state 149corresponding to OS1 with a state 149 corresponding to Risk_Lvl_1. Theresulting Risk_Lvl_1 connector workflow object 135 can performs thecorresponding branch of instructions when the management agent 145detects a state 149 specified for device state definition 155Risk_Lvl_1.

FIG. 6 shows another example user interface 108 of the managementconsole 121. The user interface can include tools for device-drivenmanagement. The management console 121 can include a workflow creationarea 403, a side panel 406, and other components as discussed.

The workflow creation area 403 can include an entry point workflowobject 603 that specifies a user or device group “group 1.” The workflowcreation area 403 can also include an if-condition workflow object 606connected to the entry point workflow object 603 without any branches orconditional actions specified. A user can drag or otherwise manipulatethe management console 121 to place a configuration workflow object 609and a configuration workflow object 612 into the workflow creation area403. While the graphical representation of the configuration workflowobject 609 states “OS1 Configs” the underlying workflow object 135 canspecify an object type as a configuration installation type and canfurther specify an identifier of an operating system corresponding to“OSL.” Likewise, an underlying workflow object 135 for therepresentation of configuration workflow object 612 can specify anobject type as a configuration installation type, and can furtherspecify an identifier of another operating system, this timecorresponding to “OS2.”

The management service 120 can analyze the workflow objects 135 that arein the workflow creation area 403 to identify recommendations to form adevice-driven management workflow 139. The management service 120 candetermine that the configuration workflow object 609 corresponds to anoperating system “OS1” while the workflow object 612 corresponds to amutually-exclusive operating system “OS2.” As a result, the managementservice 120 can determine that these workflow objects 609 and 612 canonly be used together in a single device-driven management workflow 139if there are branches that are performed in response to detected states149 for the associated operating systems.

The management service 120 can update the side panel 406 or another userinterface area of the management console 121 to include recommendations615. Recommendations 615 can include a condition workflow object 135that specifies an operating system “OS1.” The management console 121 canalso include a recommendation for a condition workflow object 135 thatspecifies an operating system “OS2.” In some cases, a user selection ofthe recommended condition workflow object 135 can cause the object toappear connected in the device-driven management workflow 139. In othercases, the user can draw the connector and drag or otherwise modify theconnector to include the recommended condition workflow object 135 thatspecifies the operating system “OS1.”

The recommendations 615 can also include recommendations based on acomprehensiveness definition 137. The management service 120 can analyzethe workflow objects 135 that are in the workflow creation area 403based on a comprehensiveness definition 137 to identifycomprehensiveness recommendations. A comprehensiveness definition 137can identify a set of device states 149 or device conditions that thedevice-driven management workflows 139 can include in order to beconsidered comprehensive for group 1 or another set of client devices106 specified by entry point workflow object 603. The management service120 can identify that there are no conditional branches corresponding tostates 149 corresponding to an untrusted network, the existence of app1,non-existence of app1, and the existence of file1 on a client device106. The management service 120 can update the recommendations toinclude conditions “Untrust_Net,” “App1_Exist,” “App1_! Exist.” and“File1_Exist.”

An administrator can decide that for this particular device-drivenmanagement workflow 139, no conditional actions or branch ofinstructions need to be performed for a certain condition. Themanagement console 121 can include a user interface element that whenselected can mark the recommendation as considered, and/or remove therecommendation. The management console 121 can include alerts 618 thatspecify workflow objects 135 and branches that are disconnected or canotherwise result in non-functionality.

FIG. 7 shows another example user interface 108 of the managementconsole 121. The user interface can include tools for device-drivenmanagement. The management console 121 can include a workflow creationarea 403, a side panel 406, and other components as discussed.Generally, this drawing shows how the management console 121 providestools to create a smart application 703 for use in a device-drivenmanagement workflow 139.

The smart application 703 can be considered a device-driven managementworkflow 139 that defines a branching set of instructions for deploymentof an application 147. The entry point workflow object 135 of the smartapplication 703 can specify an application workflow object 135, ratherthan a logical group of client devices 106. A workflow of the smartapplication 703 can be invoked and performed if the application workflowobject 135 is encountered in a device-driven management workflow 139.While this example describes a smart application 703 for deployment ofan application 147, the description is generally applicable to smartresources for deployment of a script, a database, a file or set offiles, a certificate, or another enterprise resource 129.

The smart application 703 can be a comprehensive device-drivenmanagement workflow 139 based on a comprehensiveness definition 137 forsmart applications. This enables the smart application 703 tosuccessfully provide access to an application 147 in different ways andfor a wide variety of client devices 106, based on the states 149 ofeach client device 106.

In this nonlimiting example, the smart application 703 can install anumber of policies 131 and then evaluate an if-condition based on states149 of a client device 106. In this example, the if-condition can beconfigured to evaluate whether the client device 106 is in a trusted oruntrusted geolocation or network location. If the location is untrusted,then the smart application 703 can perform a branch of instructions thatinstalls a configuration 133 for virtual desktops and then configuresthe client device 106 to access a virtual desktop version of theapplication 147.

If the location is trusted, then the smart application 703 can evaluatewhether the platform of the client device 106 is a mobile platform or adesktop platform such as macOS® or Windows®. If the platform of theclient device 106 is macOS®, then a macOS® version of the application147 can be installed. If the platform of the client device 106 isWindows®, then a Windows® version of the application 147 can beinstalled. If the platform of the client device 106 is a mobileplatform, then a single sign on process can be performed on the clientdevice 106. Thereafter, if the mobile platform of the client device 106is an Android® for Work compatible platform, then an Android® for Workpolicy 131 can be installed, since the application 147 can be a defaultapplication 147 that is preinstalled on Android® platforms. If themobile platform of the client device 106 is an iOS® platform, then aniOS® version of the application 147 can be installed.

The management console 121 can include recommendations 706 that aregenerated based on a comprehensiveness definition 137. The managementservice 120 can analyze the workflow objects 135 of the smartapplication 703 based on a comprehensiveness definition 137. Thecomprehensiveness definition 137 can identify a set of device states 149or device conditions that the device-driven management workflows 139 caninclude in order to be considered comprehensive for a smart application.

The management service 120 can determine that the comprehensivenessdefinition 137 indicates that a legacy policy 131 should be used forlegacy Android® platform client devices 106 and that the smartapplication 703 does not provide the legacy policy 131 for legacyAndroid® platform client devices 106. The management service 120 cangenerate a recommendation that provides a set of workflow objects 135that provides the legacy policy 131 for legacy Android® platform clientdevices 106. A user can drag-and-drop, select, or otherwise manipulatethe recommended set of workflow objects 135 to include it in the smartapplication 703.

The management service 120 can also determine that the comprehensivenessdefinition 137 indicates that a particular version of the application147 should be used when states 149 indicate a 64-bit versions ofWindows- and the current smart application 703 does not evaluate thisstate 149 or provide the version of the application 147. The managementservice 120 can generate a recommendation that provides a set ofworkflow objects 135 that provides the particular version of theapplication 147 for client devices 106 executing 64-bit versions ofWindows®. A user can drag-and-drop, select, or otherwise manipulate therecommended set of workflow objects 135 to include it in the smartapplication 703.

FIG. 8 shows a flowchart 800 performed by components of the networkedenvironment 100. Specifically, the flowchart 800 describes how themanagement agent 145 can execute, process, or otherwise implementdevice-driven management workflows 139 that include common dependencies141. While the flowchart 800 is described as performed by the managementagent 145, it can also be considered functionality performed by theclient device 106. Certain functionality described for the flowchart 800can also be performed by other components of the networked environment100. Segmentation and ordering indicated in the flowchart 800 is forexample purposes only. The functionality described for a particular stepcan be performed in any order relative to the other steps described.

Beginning with step 803, the management agent 145 can send a request tothe management service 120 for one or more device-driven managementworkflows 139. This could be done periodically (e.g., as part of aregular polling request or checking by the management agent 145) or inresponse to an event (e.g., registration of the client device 106 withthe management service 120).

Then at step 806, the management agent 145 can receive any device-drivenmanagement workflows 139 from the management service 120 that have beenspecified for the client device 106. For example, the management agent145 could access the command queue 123 and retrieve the device-drivenmanagement workflows 139 from the command queue 123 that were placed inthe command queue 123 by the management service 120 in response to therequest sent at step 803. The device-driven management workflows 139 canbe stored by the management agent 145 in a workflow queue 150 for laterevaluation and/or execution.

Next, at step 809, the management agent 145 can evaluate thedevice-driven management workflows 139 stored in the workflow queue 150to identify one or more common dependencies 141 between thedevice-driven management workflows 139 or individual tasks 140 specifiedor defined by the device-driven management workflows 139. For example,the management agent 145 could evaluate each of the device-drivenmanagement workflows 139 to determine which resources (e.g.,configuration files, libraries, applications 147, etc.) individual onesof the device-driven management workflows 139 specify for installation.Where the same resource (e.g., the same configuration file, the samelibrary, or the same application 147, etc.) is specified forinstallation, the management agent 145 could determine that the resourceis a common dependency 141.

Moving on to step 813, the management agent 145 can create a versionhierarchy 151 for each common dependency 141 identified at step 813. Theversion hierarchy 151 can specify the device-driven management workflows139 associated with the common dependency 141 and the version of thecommon dependency 141 specified. For example, if Workflow A specified atleast version 10 of a library as a dependency 141, Workflow B specifiedat least version 11 of the library as a dependency 141, and Workflow Cspecified at least version 8 of the library as a dependency 141, thenthe management agent 145 could create a version hierarchy 151 that listsversion 11, version 10, and version 8 of the library in descendingorder.

Then at step 816, the management agent 145 can subsequently execute orprocess one of the device-driven management workflows 139 from theworkflow queue 150. To process the device-driven management workflow139, the management agent 145 could evaluate the ASL file that definesthe device-driven management workflow 139 and implement the individualtasks 140 in the order specified.

Next at step 819, the management agent 145 can determine whether thecommon dependency 141 identified at step 809 has been installed. Thischeck may be performed because the common dependency 141 may havealready been installed (e.g., during earlier execution of anotherdevice-driven management workflow 139 that had been in the workflowqueue 150). Accordingly, the management agent 145 may avoid reinstallingthe common dependency 141 by determining whether it has already beeninstalled. If the common dependency 141 has already been installed, thenthe process skips to step 833. However, if the common dependency 141 hasnot yet been installed, then the process proceeds to step 823.

If the process proceeds to step 823, the management agent 145 canattempt to install the highest or most recent of the common dependency141. For example, the management agent 145 could reference the versionhierarchy 151 created at step 813 for the common dependency 141 todetermine which version of the common dependency 141 is the highest ormost recent version. The management agent 145 could then attempt toinstall this version of the common dependency 141.

Then at step 826, the management agent 145 can determine whetherinstallation of the common dependency 141 failed. The determinationcould be made using a variety of approaches. One approach is todetermine whether an error message or error code was returned by theinstallation process (e.g., application or library installer). Anotherapproach is to determine whether the installation process exceeded apredefined or pre-specified amount of time (e.g., “timed-out”). Ifinstallation was successful, then the process proceeds to step 836.However, if the installation were unsuccessful, then the processproceeds to step 829.

At step 829, the management agent 145 can evaluate the version hierarchy151 to determine whether any lower or older versions of the commondependency 141 are listed. For example, if the version hierarchy 151lists version 11, version 10, and version 8 of a library to be installedin descending order, and installation of version 11 had failed, themanagement agent 145 could determine that version 10 and/or version 8 ofthe library are options for installation in order to allow fordevice-driven management workflows 139 to be completed that do notdepend on version 11 of the library to be installed. Therefore, if otherversions of the common dependency 141 are listed in the versionhierarchy 151, then the management agent 145 could remove the version ofthe dependency 141 that failed to install from the version hierarchy151. The process could then return to step 823, where the managementagent 145 could attempt installation of the highest or most recentversion of the common dependency 141 that remained in the versionhierarch 151. However, if there are no other versions of the commondependency 141 listed or identified in the version hierarchy 151, thenthe process could end. In either event, the management agent 145 couldalso report to the management service that the current device-drivenmanagement workflow 139 failed to complete and/or identify thedependency 141 that failed to install.

However, if the process proceeds to step 833, the management agent 145can determine that installation of the dependency 141 can be skippedbecause another, compliant version has been already installed as part ofa previous device-driven management workflow 139. Finally, at step 836,the management agent 145 can complete the device-driven managementworkflow 139 that was initiated at step 816.

FIG. 9 shows a flowchart 900 performed by components of the networkedenvironment 100. Specifically, the flowchart 900 describes how themanagement agent 145 can coordinate the execute, process, or otherwiseimplement device-driven management workflows 139 within conflicting orpotentially conflicting time windows 142. While the flowchart 900 isdescribed as performed by the management agent 145, it can also beconsidered functionality performed by the client device 106. Certainfunctionality described for the flowchart 900 can also be performed byother components of the networked environment 100. Segmentation andordering indicated in the flowchart 900 is for example purposes only.The functionality described for a particular step can be performed inany order relative to the other steps described.

Beginning with step 901, the management agent 145 can obtain one or moretime windows 142 from the management service 120 and store them on theclient device 106 for future reference. For example, the time windows142 could be received in response to a request made by the managementagent 145 to the management service 120. As another example, themanagement agent 145 could retrieve the time windows 142 from a commandqueue 123 maintained by the management service 120, wherein the timewindows 142 were placed in the command queue 123 by the managementservice 120 in response to a request received from the management agent145. In other examples, the time windows 142 could be sent by themanagement service 120 without prompting from the management agent 145(e.g., by “pushing” the time windows 142 to the management agent 145).

Proceeding to step 903, the management agent 145 can identify thecurrent time window. This could be done by querying the system clock ofthe client device 106 to determine the date and time. The managementagent 145 could then evaluate the time windows 142 to determine whichtime window(s) 142 match, overlap, encompass, or otherwise include thecurrent date and time.

Then at step 906, the management agent 145 can determine whether adevice-driven management workflow 139 stored in the workflow queue 150can be executed based on the time window(s) 142 identified at step 903.For example, the management agent 145 could evaluate a firstdevice-driven management workflow 139 in the workflow queue 150 todetermine the type of device-driven management workflow 139 and compareit to the class(es) of the time window(s) 142 identified at step 909.For instance, if the current time falls within a time window 142 that isclassified as a maintenance window, then the management agent 145 coulddetermine that any device-driven management workflow 139 can beexecuted. As another example, if the management agent 145 determinesthat the current time falls within a time window 142 classified as“business hours,” the management agent 145 might determine that nodevice-driven management workflow 139 should be implemented to avoidimpacting a user's ability to work during business hours. If multipletime windows 142 overlap, then the time windows 142 could be comparedand a highest priority or highest ranking time window 142 could be usedto determine whether to execute the device-driven management workflow139. For example, a default time window 142 could specify that anydevice-driven management workflows 139 could be executed, but anoverlapping, higher-ranked time window 142 could specify that thecurrent date and time fall within business hours and execution of adevice-driven management workflow 139 would be prohibited. Accordingly,the higher-ranking time window 142 specifying business hours would beused by the management agent 142 to determine whether to implement thedevice-driven management workflow 139. Similarly, a default time window142 could specify that device-driven management workflows 139 are not tobe executed, while an overlapping, higher-ranked time window 142 couldspecify that the current date and time fall within a maintenance windowand execution of a device-driven management workflow 139 is permitted.As another example, a time window 142 for an emergency maintenancewindow could overlap with a time window 142 specifying business hours,in which case the time window 142 for emergency maintenance mightsupersede the time window 142 for the business hours. If a determinationis made that the device-driven management workflow 139 can be executedin the current time window 142, then the process can proceed to step909. However, if the determination is made that the device-drivenmanagement workflow 139 cannot currently be executed, then the processcan return to step 903 for continued evaluation until an appropriatetime window for execution of the device-driven management workflow 139is identified. The process at step 906 could be performed for eachdevice-driven management workflow 139 in the workflow queue 150 or theonly the first device-driven management workflow 139 in the workflowqueue

Next at step 909, the management agent 145 can execute the device-drivenmanagement workflow 139. For example, the management agent 145 couldprocess or execute individual tasks 140 specified by the device-drivenmanagement workflow 139 in the order specified. This could be done byprocessing or evaluating the Amazon State Language (ASL) file thatdefines the device-driven management workflow 139 and the tasks 140 ofthe device-driven management workflow 139.

Moving onto step 913, the management agent 145 can identify the currenttime window 142 as the task 140 or device-driven management workflow 139continues to execute. This can be done at periodic intervals (e.g.,every minute, every ten (10) minutes, every fifteen (15) minutes, everythirty (30) minutes, every hour, etc.) to determine whether thedevice-driven management workflow 139 started executing during apermissible time window 142, but is continuing execution in animpermissible time window 142. The process of step 913 can be performedin the manner previously described with respect to step 903.

Proceeding to step 916, the management agent 145 can determine whetherthe device-driven management workflow 139 is permitted to execute duringthe current time window 142. The process at step 916 could be performedin a similar manner as previously described with respect to step 906. Ifthe device-driven management workflow 139 is permitted to execute duringthe current time window 142, then the process proceeds to step 919. Ifthe device-driven management workflow 139 is not permitted to executeduring the current time window 142, then the process instead proceeds tostep 926.

If the process proceeds to step 919, the management agent 145 candetermine whether the device-driven management workflow 139 is currentlypaused. This could be done, for example, by evaluating the current state149 of the device-driven management workflow 139 or evaluating thecurrent state 149 of the client device 106 to determine whether anyprocesses associated with the device-driven management workflow 139 arecurrently executing. The device-driven management workflow 139 may havebeen paused, for example, due to the device-driven management workflow139 previously executing during a prohibited time window 142. If thedevice-driven management workflow 139 is not paused, then the managementagent 145 could conclude that the device-driven management workflow 139is currently executing and the process could proceed back to step 913.However, if the device-driven management workflow 139 is currentlypaused, the process could proceed to step 923.

Then, at step 923, the management agent 145 can unpause or otherwisecause the device-driven management workflow 139 to resume execution oroperation. For example, the management agent 145 could continueexecuting the device-driven management workflow 139 by continuing thepreviously processed task 140 or beginning the next task 140 specifiedby the device-driven management workflow 139. The process could thenreturn to step 913.

However, if the process proceeds to step 926, the management agent 145can determine whether the device-driven management workflow 139 iscurrently executing. This could be done, for example, by evaluating thecurrent state 149 of the device-driven management workflow 139 orevaluating the current state 149 of the client device 106 to determinewhether any processes associated with the device-driven managementworkflow 139 are currently executing. If the device-driven managementworkflow 139 is currently executing, then the process could proceed tostep 929. However, if the device-driven management workflow 139 is notcurrently executing, then the process could return to step 913.

If the process proceeds to step 929, the management agent 145 can pausethe device-driven management workflow 139. For example, the managementagent 145 could cause any processes currently executing to pause. Themanagement agent 145 could also save the current state 149 of the task140 of the device-driven management workflow 139 that is currently beingexecuted as well as the current state 149 of the device-drivenmanagement workflow 139 as well. As a result, the device-drivenmanagement workflow 139 could be resumed at a later point in time. Oncethe device-driven management workflow 139 is paused, the process canreturn to 913.

A number of software components previously discussed are stored in thememory of the respective computing devices and are executable by theprocessor of the respective computing devices. In this respect, the term“executable” means a program file that is in a form that can ultimatelybe run by the processor. Examples of executable programs can be acompiled program that can be translated into machine code in a formatthat can be loaded into a random access portion of the memory and run bythe processor, source code that can be expressed in proper format suchas object code that is capable of being loaded into a random accessportion of the memory and executed by the processor, or source code thatcan be interpreted by another executable program to generateinstructions in a random access portion of the memory to be executed bythe processor. An executable program can be stored in any portion orcomponent of the memory, including random access memory (RAM), read-onlymemory (ROM), hard drive, solid-state drive, Universal Serial Bus (USB)flash drive, memory card, optical disc such as compact disc (CD) ordigital versatile disc (DVD), floppy disk, magnetic tape, or othermemory components.

The memory includes both volatile and nonvolatile memory and datastorage components. Volatile components are those that do not retaindata values upon loss of power. Nonvolatile components are those thatretain data upon a loss of power. Thus, the memory can include randomaccess memory (RAM), read-only memory (ROM), hard disk drives,solid-state drives, USB flash drives, memory cards accessed via a memorycard reader, floppy disks accessed via an associated floppy disk drive,optical discs accessed via an optical disc drive, magnetic tapesaccessed via an appropriate tape drive, or other memory components, or acombination of any two or more of these memory components. In addition,the RAM can include static random access memory (SRAM), dynamic randomaccess memory (DRAM), or magnetic random access memory (MRAM) and othersuch devices. The ROM can include a programmable read-only memory(PROM), an erasable programmable read-only memory (EPROM), anelectrically erasable programmable read-only memory (EEPROM), or otherlike memory device.

Although the applications and systems described herein can be embodiedin software or code executed by general purpose hardware as discussedabove, as an alternative the same can also be embodied in dedicatedhardware or a combination of software/general purpose hardware anddedicated hardware. If embodied in dedicated hardware, each can beimplemented as a circuit or state machine that employs any one of or acombination of a number of technologies. These technologies can include,but are not limited to, discrete logic circuits having logic gates forimplementing various logic functions upon an application of one or moredata signals, application specific integrated circuits (ASICs) havingappropriate logic gates, field-programmable gate arrays (FPGAs), orother components, etc. Such technologies are generally well known bythose skilled in the art and, consequently, are not described in detailherein.

The flowcharts and sequence diagrams show the functionality andoperation of an implementation of portions of the various embodiments ofthe present disclosure. If embodied in software, each block canrepresent a module, segment, or portion of code that includes programinstructions to implement the specified logical function(s). The programinstructions can be embodied in the form of source code that includeshuman-readable statements written in a programming language or machinecode that includes numerical instructions recognizable by a suitableexecution system such as a processor in a computer system. The machinecode can be converted from the source code through various processes.For example, the machine code can be generated from the source code witha compiler prior to execution of the corresponding application. Asanother example, the machine code can be generated from the source codeconcurrently with execution with an interpreter. Other approaches canalso be used. If embodied in hardware, each block can represent acircuit or a number of interconnected circuits to implement thespecified logical function or functions.

Although the flowcharts and sequence diagrams show a specific order ofexecution, it is understood that the order of execution can differ fromthat which is depicted. For example, the order of execution of two ormore blocks can be scrambled relative to the order shown. Also, two ormore blocks shown in succession can be executed concurrently or withpartial concurrence. Further, in some embodiments, one or more of theblocks shown in the flowcharts and sequence diagrams can be skipped oromitted. In addition, any number of counters, state variables, warningsemaphores, or messages might be added to the logical flow describedherein, for purposes of enhanced utility, accounting, performancemeasurement, or providing troubleshooting aids, etc. it is understoodthat all such variations are within the scope of the present disclosure.

Also, any logic or application described herein that includes softwareor code can be embodied in any non-transitory computer-readable mediumfor use by or in connection with an instruction execution system such asa processor in a computer system or other system. In this sense, thelogic can include statements including instructions and declarationsthat can be fetched from the computer-readable medium and executed bythe instruction execution system. In the context of the presentdisclosure, a “computer-readable medium” can be any medium that cancontain, store, or maintain the logic or application described hereinfor use by or in connection with the instruction execution system.Moreover, a collection of distributed computer-readable media locatedacross a plurality of computing devices (e.g. storage area networks ordistributed or clustered filesystems or databases) may also becollectively considered as a single non-transitory computer-readablemedium.

The computer-readable medium can include any one of many physical mediasuch as magnetic, optical, or semiconductor media. More specificexamples of a suitable computer-readable medium would include, but arenot limited to, magnetic tapes, magnetic floppy diskettes, magnetic harddrives, memory cards, solid-state drives, USB flash drives, or opticaldiscs. Also, the computer-readable medium can be a random access memory(RAM) including static random access memory (SRAM) and dynamic randomaccess memory (DRAM), or magnetic random access memory (MRAM). Inaddition, the computer-readable medium can be a read-only memory (ROM),a programmable read-only memory (PROM), an erasable programmableread-only memory (EPROM), an electrically erasable programmableread-only memory (EEPROM), or other type of memory device.

Further, any logic or application described herein can be implementedand structured in a variety of ways. For example, one or moreapplications described can be implemented as modules or components of asingle application. Further, one or more applications described hereincan be executed in shared or separate computing devices or a combinationthereof. For example, a plurality of the applications described hereincan execute in the same computing device, or in multiple computingdevices in the same computing environment 103.

Disjunctive language such as the phrase “at least one of” X, Y, or Z,unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., can beeither X, Y, or Z, or any combination thereof (e.g., X; Y; Z; X or Y; Xor Z; Y or Z; X, Y, or Z, etc.). Thus, such disjunctive language is notgenerally intended to, and should not, imply that certain embodimentsrequire at least one of X, at least one of Y, or at least one of Z toeach be present.

It should be emphasized that the above-described embodiments of thepresent disclosure are merely possible examples of implementations setforth for a clear understanding of the principles of the disclosure.Many variations and modifications can be made to the above-describedembodiments without departing substantially from the spirit andprinciples of the disclosure. All such modifications and variations areintended to be included herein within the scope of this disclosure andprotected by the following claims.

What is claimed is:
 1. A system, comprising: a computing devicecomprising a processor and a memory, and machine-readable instructionsstored in the memory that, when executed by the processor, cause thecomputing device to at least: evaluate a plurality of workflows storedin a workflow queue to identify a common dependency of the plurality ofworkflows; create a version hierarchy for the common dependency of theplurality of workflows, the version hierarchy identifying multipleversions of the common dependency; in response to execution of a firstone of the plurality of workflows stored in the workflow queue, evaluatethe version hierarchy to identify the most recent version of the commondependency; and initiate installation of the most recent version of thecommon dependency.
 2. The system of claim 1, wherein themachine-readable instructions stored in the memory, when executed by theprocessor, further cause the computing device to at least: determinethat installation of the most recent version of the common dependencyhas failed; in response to a determination that the installation of themost recent version of the common dependency has failed, evaluate theversion hierarchy to identify a second most recent version of the commondependency; initiate installation of the second most recent version ofthe common dependency; and block execution of individual ones of theplurality of workflows that are dependent on the most recent version ofthe common dependency.
 3. The system of claim 2, wherein themachine-readable instructions stored in the memory, when executed by theprocessor, further cause the computing device to at least send a messageto a management service that the individual ones of the plurality ofworkflows that are dependent on the most recent version of the commondependency have failed.
 4. The system of claim 1, wherein themachine-readable instructions stored in the memory, when executed by theprocessor, further cause the computing device to at least: send arequest to a management service for the plurality of workflows; receivethe plurality of workflows from the management service; and store theplurality of workflows from the management service in the workflowqueue.
 5. The system of claim 1, wherein the common dependency is aconfiguration file.
 6. The system of claim 1, wherein the commondependency is a library to be installed on the computing device.
 7. Thesystem of claim 1, wherein the common dependency is an application to beinstalled on the computing device.
 8. A computer-implemented method,comprising evaluating a plurality of workflows stored in a workflowqueue to identify a common dependency of the plurality of workflows;creating a version hierarchy for the common dependency of the pluralityof workflows, the version hierarchy identifying multiple versions of thecommon dependency; in response to execution of a first one of theplurality of workflows stored in the workflow queue, evaluating theversion hierarchy to identify the most recent version of the commondependency; and initiating installation of the most recent version ofthe common dependency.
 9. The computer-implemented method of claim 8,further comprising determining that installation of the most recentversion of the common dependency has failed; in response to adetermining that the installation of the most recent version of thecommon dependency has failed, evaluating the version hierarchy toidentify a second most recent version of the common dependency;initiating installation of the second most recent version of the commondependency; and blocking execution of individual ones of the pluralityof workflows that are dependent on the most recent version of the commondependency.
 10. The computer-implemented method of claim 2, furthercomprising sending a message to a management service that the individualones of the plurality of workflows that are dependent on the most recentversion of the common dependency have failed.
 11. Thecomputer-implemented method of claim 8, further comprising sending arequest to a management service for the plurality of workflows;receiving the plurality of workflows from the management service; andstoring the plurality of workflows from the management service in theworkflow queue.
 12. The computer-implemented method of claim 8, whereinthe common dependency is a configuration file.
 13. The method of claim8, wherein the common dependency is a library to be installed on thecomputing device.
 14. The method of claim 8, wherein the commondependency is an application to be installed on the computing device.15. A non-transitory, computer-readable medium comprisingmachine-readable instructions that, when executed by a processor of aclient device, cause the client device to at least: evaluate a pluralityof workflows stored in a workflow queue to identify a common dependencyof the plurality of workflows; create a version hierarchy for the commondependency of the plurality of workflows, the version hierarchyidentifying multiple versions of the common dependency; in response toexecution of a first one of the plurality of workflows stored in theworkflow queue, evaluate the version hierarchy to identify the mostrecent version of the common dependency; and initiate installation ofthe most recent version of the common dependency.
 16. Thenon-transitory, computer-readable medium of claim 15, wherein themachine-readable instructions stored in the memory, when executed by theprocessor, further cause the client device to at least: determine thatinstallation of the most recent version of the common dependency hasfailed; in response to a determination that the installation of the mostrecent version of the common dependency has failed, evaluate the versionhierarchy to identify a second most recent version of the commondependency; initiate installation of the second most recent version ofthe common dependency; and block execution of individual ones of theplurality of workflows that are dependent on the most recent version ofthe common dependency.
 17. The non-transitory, computer-readable mediumof claim 16, wherein the machine-readable instructions stored in thememory, when executed by the processor, further cause the client deviceto at least send a message to a management service that the individualones of the plurality of workflows that are dependent on the most recentversion of the common dependency have failed.
 18. The non-transitory,computer-readable medium of claim 15, wherein the machine-readableinstructions stored in the memory, when executed by the processor,further cause the client device to at least: send a request to amanagement service for the plurality of workflows; receive the pluralityof workflows from the management service; and store the plurality ofworkflows from the management service in the workflow queue.
 19. Thenon-transitory, computer-readable medium of claim 15, wherein the commondependency is a library to be installed on the computing device.
 20. Thenon-transitory, computer-readable medium of claim 15, wherein the commondependency is an application to be installed on the client device.